Wireless radio access networks with asynchronous frontend

ABSTRACT

A synchronization technique for cloud radio access network (cloud RAN) to synchronize the cloud and remote radio units. The connection between cloud and remote radios is Ethernet and IEEE1588 is used to provide synchronization between baseband residing in the cloud and remote radios.

The application claims priority to the following related application andincluded here is as a reference.

Nonprovisional application: U.S. patent application Ser. No. 15/145,536filed May 3, 2016, and entitled “CLOUD BASED WIRELESS NETWORK.”

BACKGROUND

Mobile data is increasing at a compound annual rate of far more than100% as a result of an increasing level of penetration of data-intensivedevices and an increasing level of usage per device. These devices aregetting smarter due to improved user interfaces, vastly increasednumbers of applications, faster processors, and improved radio accesstechnologies, therefore are consuming increasing amounts of data.

Data volumes are growing at a rate that exceeds operators' ability togrow capacity. Capacity growth typically comes from growth in the numberof sites, from increased spectrum resources, and from enhancements inradio access technology.

Long Term Evolution (LTE) technology, standardized by the ThirdGeneration Partnership Project (3GPP), has emerged as the nextgeneration wireless technology that will lead the growth of mobilebroadband services in the next decade. Its adoption by service providersaround the world has the potential to generate economies of scaleunprecedented by any previous generation of wireless networkingtechnology as it becomes the universal 4G/5G mobile platform used by allservice providers.

LTE is critical to delivering the lower cost per bit, higher bandwidth,and subscriber experience needed to address the challenges of mobilebroadband. It has the potential to transform how subscribers andmachines use applications and content distributed over mobile andconverged networks. The effect will be to increase the value of thesenetworks and create favorable conditions for the continued mass marketadoption of mobile broadband services.

The reality is that, we have reached a point where an increase in numberof conventional sites and available spectrum can no longer keep up withthe explosion in demand for mobile data capacity—actually falling shortby an entire order of magnitude in recent years. What other optionsexist? One possibility is architectural innovation. What if thedefinition of a “cell site” were radically changed, in such a way thatthe number of “sites” dramatically increased and the cost per unit ofcapacity (after adjusting for the inevitable lower utilization ofsmaller sites) significantly decreased?

This capacity gap drives deployment of at least one order-of-magnitudemore “small cells”—making up for the difference by means of spectrumre-use. In order to provide consistent capacity density across a mobileservice area, these deployments need to take place in a more“distributed” manner—forcing operators to expand beyond the currentfoot-print for the deployment of more mobile broadband radios. In manycases, operators need to acquire more and new types of cell locations todeploy data-centric wireless broadband service networks. These celllocations then determine the required type of “small cell” equipment tobuild a heterogeneous mobile radio access network.

Operators believe Spectrum and radio access network are the mostexpensive components. OEM describes an uneven distribution of traffic.They also indicate that “50% of traffic is carried by 15% to 20% of thecells.” Small and low cost cells can support an exceptionally hightraffic density. According to a published study LTE small cells are ableto deliver as high as 200 times the traffic density of LTE macrocells.Therefore, a new and more varied radio access network (RAN) architectureis emerging, driven by the availability of new technologies, moredemanding performance, coverage and cost requirements, and innovativebusiness models. The traditional ground-based multi-sector macro basetransceiver station (BTS) is rapidly being complemented by single-sectorcells with a smaller footprint.

Time division duplex (TDD) technology has gained much attention sinceTDD can be adaptively adjusted to handle asymmetric and time-varyingtraffic. A major disadvantage of dynamic TDD (D-TDD) is severeco-channel interference (CCI) due to uplink and downlink asymmetrictransmission. The interference problem can be alleviated via using smartantennas. Intelligent time slot allocation and scheduling algorithms canalso improve the performance of D-TDD systems.

In next decade, Web-scale IT will be an architectural approach foundoperating in most of global enterprises, up from less than 10 percent in2013. Web-scale IT is a pattern of global-class computing that deliversthe capabilities of large cloud service providers within an enterpriseIT setting by rethinking positions across several dimensions.

Large cloud services providers such as Amazon, Google, Facebook, etc.,are reinventing the way in which IT services can be delivered. Theircapabilities go beyond scale in terms of sheer size to also includescale as it pertains to speed and agility. If enterprises want to keeppace, then they need to emulate the architectures, processes andpractices of these exemplary cloud providers.

Web-scale IT looks to change the IT value chain in a systemic fashion.Data centers are designed with an industrial engineering perspectivethat looks for every opportunity to reduce cost and waste. Web-orientedarchitectures allow developers to build very flexible and resilientsystems that recover from failure more quickly.

Web-scale IT refer to a global-class of computing or architecturalapproach used to deliver the capabilities of large cloud serviceproviders within an enterprise IT setting. The approach is to design,build and manage data center infrastructure where capabilities go beyondscale in terms of size to include scale as it pertains to speed andagility. Web-scale IT is simply defined as all the things happening atlarge cloud service firms, such as Google, Amazon, Netflix, Facebook andothers, that enables them to achieve extreme levels of agility andscalability by applying new processes and architectures

Web-scale IT methodology pertains to designing, deploying and managinginfrastructure at any scale and can be packaged in a number of ways tosuit diverse requirements and can scale to any size of business orenterprise. It is not a single technology implementation, but rather aset of capabilities of an overall IT system

This disclosure is a synchronization technique in a cloud radio accessnetwork (RAN) using IEEE1588.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a conventional Radio Access Network(RAN).

FIG. 2 illustrates embodiments of a packet based Radio Access Network(RAN).

FIG. 3 depicts embodiments of a Cloud RAN.

FIG. 4 shows an embodiment of Radio Head in a Cloud RAN.

FIG. 5 shows an embodiment of Cloud RAN components in a Cloud.

The drawings referred to in this description should be understood as notbeing drawn to scale except if specifically noted.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments of the presenttechnology, examples of which are illustrated in the accompanyingdrawings. While the technology will be described in conjunction withvarious embodiment(s), it will be understood that they are not intendedto limit the present technology to these embodiments. On the contrary,the present technology is intended to cover alternatives, modificationsand equivalents, which may be included within the spirit and scope ofthe various embodiments as defined by the appended claims.

Furthermore, in the following description of embodiments, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present technology. However, the present technologymay be practiced without these specific details. In other instances,well known methods, procedures, components, and circuits have not beendescribed in detail as not to unnecessarily obscure aspects of thepresent embodiments.

FIG. 1 depicts an embodiment of a conventional radio access network(RAN) 100. In general, conventional RAN 100 facilitates communicationbetween user equipment (UE) and core network. Signal sent by UE 101 isreceived by antenna 102 and translated to baseband signal by remoteradio unit 103. The baseband signal from remote radio unit 103 is sentthrough a synchronous link using common protocol for radio interface(CPRI) or other similar synchronous protocols to baseband unit 104 fordetection. The detected signal from baseband unit 104 is transported tocore network by transport unit 105.

FIG. 2 depicts one embodiment of an all packet radio access network(RAN) 200. In general, all packet RAN 200 facilitates communicationbetween user equipment (UE) and core network. Signal sent by UE 201 isreceived by antenna 202 and translated to baseband signal by remoteradio unit 203. The baseband signal from remote radio unit 203 is sentthrough an asynchronous link to baseband unit 204 in the cloud. Thedetected signal from baseband unit 204 is transported to core network bytransport unit 205.

In one embodiment the link between remote radio unit 203 and basebandunit 204 is Ethernet.

In one embodiment the link between remote radio unit 203 and basebandunit 204 is serial rapid IO (SRio).

In one embodiment the link between remote radio unit 203 and basebandunit 204 is any proprietary packet protocol.

In one embodiment the asynchronous link between remote radio unit 203and the baseband unit 204 exchange IP packets containing baseband signaland control signals.

In one embodiment the IP packets (TCP and UDP) in asynchronous linkbetween baseband unit 204 and remote radio unit 203 have CPRI, open basestation architecture initiative (OBSAI) or other synchronous protocolsencapsulated.

In one embodiment the Ethernet packets between remote radio unit 203 andbaseband unit 204 have baseband signal and control data encapsulated.

In one embodiment the Ethernet packets between remote radio unit 203 andbaseband unit 204 have CPRI, OBSAI or other synchronous protocolsencapsulated.

In one embodiment the asynchronous link between remote radio unit 203and the baseband unit 204 uses header and payload compression.

FIG. 3 illustrates an embodiment of cloud RAN 300. In general, cloud RAN300 facilitates communication between user equipment (UE) 301 and cloud307. Signal sent by UE 301 is received by antenna 302 and translated tobaseband signal by remote radio unit 303. The baseband signal from radiounit 303 is sent through an asynchronous link to the cloud 307 thataccommodates baseband unit 304, transport unit 305 and core network 306for further processing. The detected signal from baseband unit 304 istransported to core network 306 by transport unit 305.

In one embodiment of cloud RAN 300, the Ethernet protocol packets or anyproprietary protocol packets between remote radio unit 303 and cloud 307encapsulate baseband signal, control signal, and timing signal.

In one embodiment of cloud RAN 300, the Ethernet packets between remoteradio unit 303 and cloud 307 carry CPRI or other similar protocols thatcontain control data and baseband data.

FIG. 4 illustrates the architecture of remote radio unit 400 within acloud RAN. Remote radio unit 400 facilitates translation of signal fromanalog waves received from antenna system 401 to digital baseband fortransmission to the cloud using an asynchronous link between remoteradio unit and the cloud. It also translates the digital baseband signalreceived from cloud through asynchronous link to analog waves to betransmitted by antenna system 401.

Remote radio unit 400 includes, among other things, antenna system 401,transmitters and receivers 402, data converters 403, baseband signalconditioning 404, memory/baseband unit 405, Ethernet port 406, IEE1588timing system 407, and control/management 408.

In one embodiment, the antenna system 401 comprises multiple antennas tosupport diversity, MIMO and multi-point operation. It also could providefiltering, power amplification and low noise amplification.

The receivers/transmitters unit 402 perform the task of down conversionof radio frequency signals received from antenna system 401 to basebandor low IF signals and up converting the baseband and IF signals to radiofrequency signals for antenna system 401 to transmit.

The data converter 403 does the task of analog to digital and digital toanalog conversion. Data converter 403 inputs and outputs are basebandsample streams.

The baseband sample streams from/to data converter 403 are conditionedin baseband signal conditioning 404.

The baseband signal conditioning 404 can perform AGC, crest factorreduction (CFR), digital pre-distortion (DPD), equalization, beamforming and other baseband signal conditioning.

In one embodiment of remote radio unit 400, the baseband signalsreceived from cloud through asynchronous link are first stored in amemory/baseband unit block 405 based on their transmitted time stamp orsequence number before being formatted, processed and sent to signalconditioning 404 and converter 403 for transmission.

In one embodiment, the memory size of the memory/baseband unit block 405is far more than the maximum delay jitter of Ethernet packets, SRiopackets, and proprietary packets received from the cloud.

In one embodiment of the remote radio unit 400, the Ethernet packetspayloads and proprietary packets payloads received from cloud throughasynchronous link have a remote radio identifier field, are timestamped, and have a sequence number.

In one embodiment, the Ethernet packet's payload is stored in the memoryof memory/baseband unit block 405 based on their time stamp and sequencenumber to avoid any early and late Ethernet packets.

In one embodiment, the memory/baseband unit block 405 uses the timingand control information obtained from IEEE1588 timing system block 407and control/management block 408 to process various baseband signalstreams for baseband conditioning block 404.

The formatting and processing of the baseband signal in memory/basebandunit block 405 can be controlled by control/management block 408.

In one embodiment, the baseband signal exchange between the basebandunit in the RRU and the baseband unit in the cloud or centralizedbaseband unit is baseband frames.

In one embodiment, the memory/baseband unit block 405 uses the timingand control information obtained from IEEE1588 timing system block 407and control/management block 408 to format, process, time stamp, number,and tag various baseband signal streams received from baseband unit 405for transmission to the cloud or a centralized baseband unit throughEthernet port 406.

In one embodiment the Ethernet packets received from cloud or any nodesin the path between cloud and remote radio 400 carry IEEE1588 timinginformation.

The Ethernet block 406 provides the physical layer for the remote radiounit 400 Ethernet port.

In one embodiment, the Ethernet block 406 identifies the IEEE1588 timingpackets, control/management packets, and baseband signal packetsreceived from cloud and send them to IEEE1588 timing system block 407,control/management block 408, and memory/baseband unit block 405.

In one embodiment, the Ethernet block 406 receives the IEEE1588 timingpackets, control/management packets, and baseband signal packets fromIEEE1588 timing system block 407, control/management block 408, andmemory/baseband unit block 405 and sends them to the cloud.

In one embodiment, the IEEE1588 timing system block 407 receives thetiming packets from Ethernet block 406 and retrieve synchronization andtime of the day information.

In one embodiment, the IEEE1588 timing system 407 through the Ethernetblock 406 communicates and exchange timing packets with an independentnode in the transport network to obtain and maintain clocksynchronization and time of the day.

In one embodiment, the IEEE1588 timing system block 407 uses the clocksynchronization information to create clocks and reference frequenciesfor the entire remote radio unit 400.

In one embodiment, the IEEE1588 timing system block 407 shares time ofthe day information with control/management block 408 andmemory/baseband unit block 405.

In one embodiment, the IEEE1588 timing block 407 can use SYNCE or othersynchronization techniques (assisted GPS, NTP, etc.) for synchronizingremote radio unit 400.

In another embodiment the baseband signal packets received from thecloud or centralized baseband unit are stored in the memory/basebandunit 405 based on their time stamp and then are formatted and processed.

In another embodiment the baseband signal packets received from thecloud or centralized baseband unit are stored in the memory/basebandunit 405 based on their sequence number and then are formatted andprocessed.

The control/management block 408 performs control and management of theremote radio unit 400.

In one embodiment, the control/management block 408 helps to initializeall the blocks in remote radio unit 400 at power up or reset.

In one embodiment, the control/management block 408 monitors the remoteradio unit 400 for any alarm or mal-function and report the collectedinformation to cloud.

In one embodiment, the control/management block 408 based on controldata received from cloud configures memory/baseband unit 405 to performspecific formatting and baseband processing compliment to the basebandprocessing in the cloud.

In one embodiment, the control/management block 408 based on controldata received from the cloud configures the function of memory/basebandunit 405 which is complement to the function of baseband unit in thecloud in real time.

In one embodiment the control/management block 408 configures theoperating frequency RRU, bandwidth of RRU and functions ofmemory/baseband unit 405 to complement the functions of baseband unit inthe cloud.

In one embodiment the control/management block 408 in real timeconfigures the operating frequency RRU, bandwidth of RRU and functionsof memory/baseband unit 405 to complement the functions of baseband unitin the cloud.

In another embodiment the real time configuration of memory/basebandunit 405 is based on the traffic load or other reasons (such asinterference, performance, power consumption, and etc.) identified inthe cloud.

In another embodiment the configuration of memory/baseband unit 405 isbased on initial configuration defined in the cloud.

In another embodiment the initial configuration of memory/baseband unit405 that is defined by the cloud does not change and depends on theinitial network configuration.

In one embodiment the control signals from the cloud have time stamp orsequence number.

In one embodiment, the control/management block 408 works as part ofcloud RAN Self Organizing Network (SON) and carry out tasks required bySON.

In one embodiment the RRU is an internet of things (IoT).

FIG. 5 illustrates an embodiment of cloud RAN 500. In general, cloud RAN500 facilitates communication between user equipment (UE) 501 and corenetwork 507. Signal sent by UE 501 is received by antenna 502 andtranslated to baseband signal by remote radio unit 503. The basebandsignal from remote radio unit 503 with IEEE1588 timing is sent throughasynchronous link to the cloud 504 that accommodates baseband unit 505,transport unit 506, core network 507, IEEE1588 system timing 508,control/management 509 and Ethernet port 510. The information frombaseband unit 505 is transported to core network 507 by transport unit506.

In one embodiment, the cloud RAN 500 uses IEEE1588 to synchronize thecloud 504 with the network.

In one embodiment, the cloud RAN 500 uses IEEE1588 to synchronize thecloud 504 with remote radio unit 503.

In one embodiment of the cloud RAN 500, the Ethernet packets received bycloud 504 from remote radios (remote radio 503 being one of them)through asynchronous link have a remote radio identifier and are timestamped, have a sequence number or both.

In one embodiment of the cloud RAN 500, the Ethernet encapsulates theinformation signal, the control signal, and the synchronization signal.

In one embodiment of the cloud RAN 500, the encapsulated informationsignal is the baseband frames.

In one embodiment of the cloud RAN 500, the information signal receivedfrom RRU have time stamp or sequence number and are stored based on theorder of their transmission time and sequence number.

In one embodiment of the cloud RAN 500, the control signals from RRUhave time stamp or sequence number.

In one embodiment, the baseband unit 505 uses memory blocks to store thebaseband signal received from remote radios (remote radio 503 being oneof them) based on their identifier, time tag or sequence number to avoidany early and late Ethernet packets.

In one embodiment the remote radio unit is an IoT (internet of things)

In one embodiment the remote radio unit (RRU) uses an IP address as anidentifier.

In one embodiment, the memory size of the baseband unit block 505 is farmore than the maximum delay jitter of Ethernet packets received from theremote radios (remote radio 503 being one of them).

In one embodiment the baseband unit 505 stores the received basebandsignal from remote radio unit (RRU) based on their time stamp and thenformat and process them.

In one embodiment the baseband unit 505 stores the received basebandsignal from remote radio unit (RRU) based on their sequence number andthen format and process them.

In one embodiment, the baseband unit 505 uses the timing and controlinformation obtained from IEEE1588 system timing block 508 andcontrol/management block 509 to format received baseband signal streamsfor processing.

In one embodiment, baseband unit 505 processes the received basebandsignal to provide information data for transport layer 506.

In one embodiment, the baseband unit 505 uses the timing and controlinformation obtained from IEEE1588 system timing block 508 andcontrol/management block 509 to format, time stamp, number and tagvarious baseband signal streams for transmission to remote radios(remote radio 503 being one of them).

The Ethernet block 510 provides the physical layer for the cloud 504Ethernet port.

In one embodiment, the Ethernet block 510 identifies the IEEE1588 timingpackets, control/management packets, and baseband signal frames orpackets and sends them to IEEE1588 system timing block 508,control/management block 509, and baseband unit 505.

In one embodiment, the Ethernet block 508 receives the IEEE1588 timingpackets, control/management packets, and baseband signal frame orpackets from IEEE1588 system timing block 508, control/management block509, and baseband unit 505 and sends them to remote radios (remote radio503 being one of them).

In one embodiment, the IEEE1588 system timing block 508 receives thetiming packets from Ethernet block 510 and retrieve synchronization andtime of the day information.

In one embodiment, the IEEE1588 system timing block 508 through theEthernet block 510 communicates and exchange timing packets with anothernode in the network to obtain and maintain synchronization and time ofthe day.

In one embodiment, the IEEE1588 system timing block 508 uses the clocksynchronization information to create clocks and reference frequenciesfor the cloud 504.

In one embodiment, the IEEE1588 system timing block 508 shares time ofthe day information with control/management block 509 and baseband unit505.

In one embodiment, the IEEE1588 system timing block 508 can use SYNCE orother synchronization techniques (assisted GPS, NTP, etc.) forsynchronizing remote radios (remote radio 503 being one of them) and thecloud 504.

The control/management block 509 performs control and management of thebaseband unit 505, IEEE1588 system timing 508, and transport unit 506.

In one embodiment, the control/management block 509 monitors the cloud504 for any alarm or mal-function and report the collected informationto higher layers.

In one embodiment the control/management 509 configures baseband unit505 for formatting and processing the received baseband signal from RRU.

In one embodiment the control/management 509 configures baseband unit505 for formatting and processing the transmit baseband signal sent toRRU.

In one embodiment the control/management 509 configures the specificfunctions that baseband unit 505 needs to perform and send a controlsignal to the RRU to configure RRU baseband unit to perform functionsthat complement the baseband functions in baseband unit 505.

In one embodiment the control/management 509 configures the specificfunctions that baseband unit 505 needs to perform in real time and senda control signal to the RRU to configure RRU baseband unit to performfunctions that complement the baseband functions in baseband unit 505.

In one embodiment the control/management 509 configures the specificfunctions that baseband unit 505 needs to perform in real time based ontraffic load, performance, interference, power saving, and otherreasons.

In one embodiment, the control/management block 509 based on the controldata received from remote radios (remote radio 503 being one of them)provides control for baseband signal streams formatting and processingin baseband unit 505.

In one embodiment, the control/management block 509 works as part ofcloud RAN Self Organizing Network (SON) and carry out tasks required bySON.

Various embodiments are thus described. While particular embodimentshave been described, it should be appreciated that the embodimentsshould not be construed as limited by such description, but ratherconstrued according to the following claims.

1. A cloud radio access network (CRAN) system comprising: a cloud with abaseband unit to process a received baseband signal from a remote radiounit (RRU), a transmit baseband signal for transmission to the RRU, andmaintain the cloud network synchronization and time of the day using acloud IEEE1588 (Institute of Electrical and Electronics Engineering1588) timing; said RRU consists of a baseband unit to process saidtransmit baseband signal from said baseband unit in the cloud and a RRUIEEE1588 timing to maintain clock synchronization with said basebandunit in the cloud and time of the day; an asynchronous link between saidRRU and at least said baseband unit in the cloud and a centralizedbaseband unit using at least an Ethernet packet protocol, a Serial I/O(SRio) packet protocol and a proprietary packet protocol to carry anencapsulated signal consisting of at least one of an information signal,a control signal and a synchronization signal; said information signalcontains a baseband frame or packet; said baseband unit in the RRU andsaid baseband unit in the cloud use at least one of the time of the dayand an integer number to assign at least one of a time stamp and asequence number to said information signal that is sent to said basebandunit in the cloud and said baseband unit in the RRU respectively; saidbaseband unit in the RRU uses at least one of said time stamp and saidsequence number assigned by said baseband unit in the cloud to storesaid information signal based on the order of at least one oftransmitted time stamp and transmitted sequence number and then formatand process for transmission over the air; said baseband unit in thecloud uses at least one of said time stamp and said sequence numberassigned by said baseband unit in the RRU to store said informationsignal based on the order of at least one of transmitted time stamp andtransmitted sequence number and then format and process.
 2. The cloudradio access network (CRAN) system of claim 1, wherein said informationsignal sent to the cloud from said RRU baseband unit is the receivedbaseband signal in the cloud.
 3. The cloud radio access network (CRAN)system of claim 1, wherein said information signal sent to the RRU fromsaid cloud baseband unit is the transmit baseband signal in the RRU. 4.The cloud radio access network (CRAN) system of claim 1, wherein the RRUIEEE1588 timing uses timing information to create synchronized clocksand reference frequencies for the remote radio unit.
 5. The cloud radioaccess network (CRAN) system of claim 1, wherein said asynchronous linkbetween said RRU and said cloud uses header compression.
 6. The cloudradio access network (CRAN) system of claim 1, wherein, the memory sizeof the RRU baseband unit and the cloud baseband unit exceeds a maximumdelay jitter of the transmit baseband signal packets received from thecloud and the received baseband signal packet from the RRU.
 7. The cloudradio access network (CRAN) system of claim 1, wherein said basebandframe or packet have at least one of a RRU identification number, timestamp, sequence number, IP address or code.
 8. The cloud radio accessnetwork (CRAN) system of claim 1, wherein said synchronization signalIEEE1588 signal and has at least one of a time stamp and a sequencenumber.
 9. A remote radio unit (RRU) within a cloud radio access network(CRAN) comprising: a RRU baseband unit to perform at least one of store,format, and process a baseband signal received from a baseband unit inthe cloud; said RRU baseband unit performs at least one of store,format, and process a baseband signal sent to said baseband unit in thecloud; said RRU baseband unit performs functions that are complement tofunctions in said baseband unit in the cloud; a RRU control andmanagement unit that communicates with the cloud and configures saidRRU; said RRU control and management unit configures the RRU basebandunit to perform at least one of formatting function and processingfunctions that are complement to said baseband unit in the cloud; saidRRU control and management unit configures the RRU baseband unit in realtime to perform at least one of formatting function and processingfunctions that are complement to said baseband unit in the cloud. 10.The remote radio unit explained in claim 9, wherein said RRU control andmanagement unit configures the RRU baseband unit in real time based ontraffic load identified by the cloud.
 11. The remote radio unitexplained in claim 9, wherein said RRU control and management unitconfigures the RRU baseband unit in real time based on performancedegradation identified by the cloud.
 12. The remote radio unit explainedin claim 9, wherein said RRU control and management unit configures theRRU baseband unit in real time based on interference identified by thecloud.